gnus-show-threadsnil, no threading will be done, and all of the
rest of the variables here will have no effect. Turning
threading off will speed group selection up a bit, but it is
sure to make reading slower and more awkward.gnus-thread-hide-subtreenil, all threads will be hidden when the
summary buffer is generated.
This can also be a predicate specifier (see Predicate
Specifiers). Available predicates are
gnus-article-unread-p and
gnus-article-unseen-p.
Here's an example:
(setq gnus-thread-hide-subtree
'(or gnus-article-unread-p
gnus-article-unseen-p))
(It's a pretty nonsensical example, since all unseen
articles are also unread, but you get my drift.)
gnus-thread-expunge-belowgnus-thread-score-function) less than this number
will be expunged. This variable is nil by default,
which means that no threads are expunged.gnus-thread-hide-killednil, the subtree
will be hidden.gnus-thread-ignore-subjectnil, which is the default, the
subject change is ignored. If it is nil, a change
in the subject will result in a new thread.gnus-thread-indent-levelgnus-sort-gathered-threads-functiongnus-thread-sort-by-number, responses can end up
appearing before the article to which they are responding to.
Setting this variable to an alternate value (e.g.
gnus-thread-sort-by-date), in a group's parameters
or in an appropriate hook (e.g.
gnus-summary-generate-hook) can produce a more
logical sub-thread ordering in such instances.